Hey @enguerranws,

Thanks a lot for the PR!

I first I did this review to improve consistency with the rest of the project: 765f233

But in the end I did even simpler.

I don't think we need to have a separate RadiRichButton. We can just infer it's rich by the use of illustations.
The drawback is that we can't enforce at the type level that if there is one radio that has an illustration all radio must have one but I think it's really no big deal.

I don't think we need to have a separate RadiRichButton. We can just infer it's rich by the use of illustations.
The drawback is that we can't enforce at the type level that if there is one radio that has an illustration all radio must have one but I think it's really no big deal.

I thought about that, but I wanted to stick the DSFR's components (where Radio buttons and Radio rich are presented as different components), but that's fine for me!

I thought about that, but I wanted to stick the DSFR's components (where Radio buttons and Radio rich are presented as different components), but that's fine for me!

Oh! Is that so? In that case you probably made the right call.
Anyway, now that it's published do you think I should rollback or keep it like this?

I can rollback the last commit if you think it's best. Idk